Better docstring coverage workflow from 2021 GA Hackathon #1981
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Implementation the workflow I submitted to the 2021 GitHub Actions Hackathon on dev.to: https://github.com/epassaro/docstr-cov-workflow/
This workflow has some kind of approval from the developers of the
docstr-coverage
package.Advantages:
tardis-bot
username so required minor tweakingMotivation and context
How has this been tested?
The coverage pipeline itself. Some steps requires merging to see if everything works.
Examples
Type of change
Checklist